Subject: RFC1795 on Data Link Switching (forward)

From: Wayne Clark <[email-masked]>
Date: Tue, 25 Apr 95 14:54:20 EDT

To the AIW DLSw RIG -

    Attached below is the IETF announcement for the new DLSw informational
    RFC.

    See you next week in San Jose.

Regards,
-------
Wayne Clark
cisco Systems, Inc.
Research Triangle Park, NC
[email-masked]
919.472.2958

------- Forwarded Message

Date:    Tue, 25 Apr 95 09:33:55 -0800
From:    "Joyce K. Reynolds" <[email-masked]>
To:      IETF-Announce:;
cc:      [email-masked]
Subject: RFC1795 on Data Link Switching

- --NextPart

A new Request for Comments is now available in online RFC libraries.

        RFC 1795:

        Title:      Data Link Switching: Switch-to-Switch Protocol
                    AIW DLSw RIG: DLSw Closed Pages, DLSw Standard 
                    Version 1.
        Author:     L. Wells, Chair & A. Bartky, Editor
        Date:       April 1995
        Mailbox:    [email-masked], [email-masked]
        Pages:      91
        Characters: 214,848
        Obsoletes:  1434

        URL:        ftp://ds.internic.net/rfc/rfc1795.txt

This RFC describes use of Data Link Switching over TCP/IP. The RFC is
being distributed to members of the Internet community in order to
solicit their reactions to the proposals contained in it.  While the
issues discussed may not be directly relevant to the research problems
of the Internet, they may be interesting to a number of researchers
and Implementers.  This RFC was created as a joint effort of the
Advanced Peer-to-Peer Networking (APPN) Implementers Workshop (AIW)
Data Link Switching (DLSw) Related Interest Group (RIG).  The APPN
Implementers Workshop is a group sponsored by IBM and consists of
representatives of member companies implementing current and future
IBM Networking interoperable products.  The DLSw Related Interest
Group was formed in this forum in order to produce a single version of
the Switch to Switch Protocol (SSP) which could be implemented by all
vendors, which would fix documentation problems with the existing RFC
1434, and which would enhance and evolve the protocol to add new
functions and features.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email-masked].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email-masked] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email-masked]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email-masked].  Please consult RFC 1543, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

- --NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

- --OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="[email-masked]"

Content-Type: text/plain
Content-ID: <[email-masked]>

SEND /rfc/rfc1795.txt

- --OtherAccess
Content-Type:   Message/External-body;
        name="rfc1795.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <[email-masked]>

- --OtherAccess--
- --NextPart--

------- End of Forwarded Message